Scannerless venue entry and location techniques

ABSTRACT

When attending an event at a venue, the attendee typically presents ticket information that is scanned by a venue scanner. The process associated with scanning can be dispensed with, which can improve attendee experiences, reduce costs associated with managing a venue, as well as other advantages. For example, instead of scanning a ticket at a point of ingress to the venue, a device of the user can self-scan the ticket, and then present indicia that indicates this process has occurred. The indicia can be presented to a guest services representative, who can verify that a valid ticket was redeemed by merely observing the indicia and without scanning.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to U.S.patent application Ser. No. 14/281,483 filed on May 19, 2014 andentitled, “SCANNERLESS VENUE ENTRY AND LOCATION TECHNIQUES,” whichclaims priority to U.S. Provisional Application Ser. No. 61/926,147filed on Jan. 10, 2014 and entitled, “MECHANISMS FOR IMPROVING VENUEEVENT EXPERIENCES.” The entireties of these applications areincorporated herein by reference.

TECHNICAL FIELD

This disclosure generally relates to facilitating entry to a venuewithout the need to manually scan a ticket or other information, whichcan be accomplished by leveraging location techniques such as, e.g.,audio-based signals.

BACKGROUND

When attending an event held at a venue such as a concert or sportingevent, it is customary that each attendee is greeted at a point ofingress by a guest service representative, where a ticket or otherindication of a privilege to enter the venue is verified. Typically,this verification is accomplished by the guest services representativewho, using a scanner of some type, scans the ticket or ID of theattendee. Upon successful authorization, the guest servicesrepresentative then allows the attendee entry to the venue. Such mightbe in an open entryway or one regulated with access-limiting devicessuch as turnstiles or the like.

SUMMARY

The following presents a simplified summary of the specification inorder to provide a basic understanding of some aspects of thespecification. This summary is not an extensive overview of thespecification. It is intended to neither identify key or criticalelements of the specification nor delineate the scope of any particularembodiments of the specification, or any scope of the claims. Itspurpose is to present some concepts of the specification in a simplifiedform as a prelude to the more detailed description that is presented inthis disclosure.

Systems and methods disclosed herein relate to scannerless venue entry.A proximity component can be configured to receive data that indicatesthe system is within a defined distance range from a point of ingress toa venue. A redemption component can be configured to identify ticketdata representing a privilege to enter the venue in response to theproximity data. A presentation component can be configured to instruct auser interface to present verification data representing a verificationthat the privilege to enter the venue was validated

The following description and the drawings set forth certainillustrative aspects of the specification. These aspects are indicative,however, of but a few of the various ways in which the principles of thespecification may be employed. Other advantages and novel features ofthe specification will become apparent from the following detaileddescription of the specification when considered in conjunction with thedrawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Numerous aspects, embodiments, objects and advantages of the presentinvention will be apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings, inwhich like reference characters refer to like parts throughout, and inwhich:

FIG. 1 illustrates a block diagram of an example system that can providefor scannerless venue entry in accordance with certain embodiments ofthis disclosure;

FIG. 2A provides a block diagram illustration that depicts an examplepresentation with regard to proximity data being triggered by user inputin accordance with certain embodiments of this disclosure;

FIG. 2B provides a block diagram illustration that depicts an examplepresentation with regard to triggering proximity data being transmittedby a transmitter and/or being received by the system in accordance withcertain embodiments of this disclosure;

FIG. 3A provides a block diagram illustration that depicts an examplewhere verification data is presented visually in accordance with certainembodiments of this disclosure;

FIG. 3B provides a block diagram illustration that depicts an example inwhich verification data is presented in an audible manner in accordancewith certain embodiments of this disclosure;

FIGS. 4A-C illustrate various block diagram illustrations that depictseveral example presentations of the verification data that includescertification data in accordance with certain embodiments of thisdisclosure;

FIG. 5 illustrates a block diagram of a system that can facilitateprovision of venue-specific location data that can be utilized by awide-range of attendee devices in accordance with certain embodiments ofthis disclosure;

FIG. 6 illustrates a block diagram of a system that can provide for theattendee device operating as a transmitter, which can facilitateadditional aspects of scannerless entry in accordance with certainembodiments of this disclosure;

FIG. 7 illustrates a block diagram of an example system that can providefor facilitating scannerless entry to a venue based on attendeeidentification data in accordance with certain embodiments of thisdisclosure;

FIG. 8 illustrates an example methodology that can provide forscannerless venue entry in accordance with certain embodiments of thisdisclosure;

FIG. 9 illustrates an example methodology that can provide foradditional features or aspects in connection with providing scannerlessvenue entry and audio-based location techniques in accordance withcertain embodiments of this disclosure;

FIG. 10 illustrates an example schematic block diagram for a computingenvironment in accordance with certain embodiments of this disclosure;and

FIG. 11 illustrates an example block diagram of a computer operable toexecute certain embodiments of this disclosure.

DETAILED DESCRIPTION

Overview

As used herein, the term “scannerless” is used in connection with ticketinformation and/or entry to a portion of a venue and refers toverification of access to the portion of the venue that is not dependenton the ticket information being scanned by a guest servicesrepresentative or other venue employee. The subject matter describedbroadly relates to various techniques or mechanisms that can be utilizedin connection with events (e.g., live events) held at a venue (e.g.,stadium, arena, amphitheatre, theme park, etc.). These techniques ormechanisms can be ticketing-oriented, seating-oriented, location-based,or the like; and can be directed to enhancing efficiency, availablefeatures, commemoration, conservation, incentives, security, or theexperiences associated with event attendees (e.g., a ticket purchaser),event performers (e.g., artists, athletes, etc.), event hosts (e.g.,venue owners, operators, etc.), event vendors or sponsors, or othersuitable parties or entities.

Historically, event attendees typically appeared at the event with aticket. Recently, an alternative model, denoted herein as “FlashSeats®,” was introduced, which associated a ticket purchase or othercontractual right to enter an event or venue with a user account. Thisassociation with a user account has led to numerous advantages inconnection with the domain and is, in some implementations, assumed inconnection with concepts or embodiments disclosed herein. As one exampleadvantage, because of the association with a user account, entry to thevenue can be gained by producing at the gate an ID of some type ratherthan a barcode or ticket. Therefore, as used herein the term “ticket” isintended to refer to data relating to a privilege to enter, includingconventional ticket data as well as ID-based data such as that utilizedby Flash Seats® embodiments. The ID can be a conventional driver'slicense, passport, credit card, but can also relate to data stored on auser device such as a visual image, voice signatures or othersignatures, an audio-based signal or watermark, device ID, individualID, biometric data such as a fingerprint, retina, or DNA, etc. Thedevice that stores such data (referred to herein as an “attendeedevice”) can be any suitable device such as a smart phone, tablet,wearable device, or the like.

As introduced above, when attending an event held at a venue such as aconcert or sporting event, it is customary that each attendee is greetedat a point of ingress by a guest service representative, where a ticketor other indication of a privilege to enter the venue is verified.Typically, this verification is accomplished by the guest servicesrepresentative who, using a scanner of some type, scans the ticket or IDof the attendee. Upon successful authorization, the guest servicesrepresentative then allows the attendee entry to the venue or event.Manually scanning tickets of venue attendees represents a significantexpense and might lead to inconvenience for attendees, for example, whenlines form.

Efficiencies associated with validating a potential attendee's privilegeof entry can be enhanced by enabling scannerless entry, wherein it isnot necessary for the guest service representative to spend timescanning data provided by each and every attendee. For example, theattendee device is capable of maintaining data associated with a ticket,which can be leveraged to allow the device to effectively self-scan theticket instead of ticket data being scanned by the guest servicerepresentative associated with the venue.

As one example, an application executing on the attendee device canreceive proximity data that indicates the device is near to a point ofingress to the venue, and optionally time data associated with a starttime of the event held at the venue, which can be compared with acurrent time. Proximity data can be based on any suitable technique ortechnology and can be transmitted via passive or active techniques. Forexample, proximity data can be based on GPS or other triangulationtechniques, device-based geo-location, Bluetooth, radio frequencyidentification (RFID), wireless location, near field communication(NFC), light-based or audio-based signaling techniques, magnetic-basedsignaling techniques, and so on. Additionally or alternatively,proximity data can be based on input from a user of the device such asthe user provides input indicating he or she is at the venue and wantsto redeem the ticket.

In response, the application can cause a user interface (e.g., adisplay, speakers, etc.) associated with the device to presentcertification data representing the device has redeemed a valid ticketor otherwise certified a privilege of entry to the venue. Thispresentation can be a defined background or other image, possiblyincluding a watermark, certificate of authentication (COA), a code ofthe day, etc. Additionally or alternatively the presentation can be asound clip that plays, which might also include an audio COA.Thereafter, the attendee might simply present the device (that ispresenting the indicia) to a guest service representative who canquickly verify the presentation without the time and/orresource-intensive process of scanning a ticket. The guest servicesrepresentative can quickly verify the correct elements are beingpresented by the attendee device and allow entry without the need toscan.

In some embodiments, proximity data can be received based on detectionof an audio signal. For example, points of ingress to the venue caninclude audio beacons or transmitters that produce an identifiable audiosignal, which need not necessarily be audible to human sensoryperception. Upon detection of this audio signal, the attendee device canprovide proximity data to the application. Such a technique has manyadvantages. For example, audio signals can be detected with hardware(e.g., a microphone) that is near-universal among attendee devices andtherefore can be utilized in connection with a very large set ofdevices, even those without access to GPS or other location-basedsoftware or equipment and can be utilized with very little batterydrain. In addition, many location-based techniques rely on a functioningcommunication networks, many of which are prone to congestion, poorquality of service, or unavailability when many thousands of people areclustered in a small area, such as at a venue during an event.Therefore, techniques that rely on a network connection can have reducedviability that is not an issue for audio signaling techniques.Furthermore, audio signals can be precisely configured for specifiedranges at particular locations, such as point of ingress to the venue.Additionally or alternatively, equipment for producing audio (or othertypes) of signals can be situated at various locations within the venueto facilitate location services such as guidance or navigation,proximity-based alerts, and so forth.

Furthermore, “ticketless” embodiments can exist in which either a venuedevice or an attendee device (e.g., smart device, RFID dot, etc.) canfacilitate identification. Such identification can be based on biometricdata, facial recognition techniques, or the like. Moreover, attendeedevices can operate as passive signaling devices (e.g., RFID dot, etc.)or active signaling devices (e.g., very low power active signals such aswatch battery powered RFID or Bluetooth-based, etc.).

In some embodiments, the device of the attendee can operate as an audiosignaling device similar to the functioning of the venue transmitterdevices. For example, the device can present an audio signal thatappropriately certifies a privilege of entry instead of requiring ascanner device to scan visual indicia such as a ticket, ID, barcode,etc.

In some embodiments, a single attendee device can manage and/or verifyprivileges of entry to the venue for multiple attendees. In someembodiments, the subject matter disclosed herein can be utilized inconnection with exit scanning that determines an attendee is exiting thevenue. Exit scanning can provide data that is not typically available tomany conventional approaches

Example Systems for Scannerless Venue Entry and Location Techniques

Various aspects or features of this disclosure are described withreference to the drawings, wherein like reference numerals are used torefer to like elements throughout. In this specification, numerousspecific details are set forth in order to provide a thoroughunderstanding of this disclosure. It should be understood, however, thatcertain aspects of this disclosure may be practiced without thesespecific details, or with other methods, components, materials, etc. Inother instances, well-known structures and devices are shown in blockdiagram form to facilitate describing the subject disclosure.

Referring now to FIG. 1, a system 100 is depicted. System 100 can, interalia, provide for scannerless venue entry, which can be employed inconnection with existing barcode approaches or with Flash Seats® IDapproaches. In either case, an attendee acquires (e.g., purchases) aticket to an event held at a venue, and associated information is storedon an attendee device (e.g., attendee device 120) such as a mobile phoneor wearable device. System 100 and/or attendee device 120 can include amemory that stores computer executable components and a processor thatexecutes computer executable components stored in the memory, examplesof which can be found with reference to FIG. 10. It is to be appreciatedthat the computer 1002 can be used in connection with implementing oneor more of the systems or components shown and described in connectionwith FIG. 1 and other figures disclosed herein. As depicted, system 100can also include proximity component 102, redemption component 110, andpresentation component 114, which are further detailed herein.

Upon arrival at a venue, potential attendees are typically met at thegate or other point of ingress (e.g., point of ingress 108) by a guestservices representative equipped with a scanner of some type. With thisscanner, the guest services representative will typically scan thetickets of incoming attendees. The scanner device can be incommunication with an access control server (ACS) that can verify thatthe information scanned relates to a valid ticket and that the tickethas not already been redeemed. It is understood a given venue can havemultiple points of ingress 108 and point(s) of ingress 108 can besubstantially any location or area where venue attendees gain access toportions of the venue. For example, point of ingress 108 can be a mainentry gate to the venue or to a parking area or an entry point to aspecific section (e.g., VIP lounge) of the venue. As explained, point ofingress 108 will typically be populated with one or more guest servicesrepresentatives, who, in other approaches use scanners to scan ticketdata for each attendee prior to allowing the attendee entrance to thevenue. However, in accordance with the described subject matter, theguest services need not perform any scanning. Thus, one or more pointsof ingress 108 can be designated for self-scanning and the associatedguest services representatives do not need to scan information providedby attendees and need not be equipped with a scanning device at all.

In that regard, proximity component 102 can be configured to receiveproximity data 104. Proximity data 104 can indicate that system 100 (andby extension attendee device 120 as well as the attendee) is within adefined distance 106 from a point of ingress 108 to a venue. Redemptioncomponent 110 can be configured to identify and/or validate ticket data112 representing a privilege to enter the venue. Redemption component110 can perform this validation in response to proximity component 102receiving proximity data 104. Hence, ticket data 112 can be redeemedonce it is indicated (via receipt of proximity data 104) that theattendee is near to point of ingress 108.

Once ticket data 112 has been redeemed, presentation component 114 canbe configured to instruct user interface 116 to present verificationdata 118 representing a verification that the privilege to enter thevenue was validated. Accordingly, user interface 116 can present indiciato indicate that ticket data 112 exists and was processed/redeemed.Thus, guest services representatives at point of ingress 108, instead ofmanually scanning ticket information presented by an attendee, canobserve user interface 116 to ensure the correct indicia associated withverification data 118 is being presented. If so, then the attendee canbe allowed access to the venue via a process that is secure and moreefficient than other approaches. In some embodiments, guest servicesrepresentatives need not examine every attendee, but rather can employ“spot checks,” whereby some portion of attendees are selected andchallenged and their associated devices examined for the correctindicia. In some embodiments, guest services representatives can beprompted to select a particular attendee based on information receivedthat indicates a conflict or a high probability of a conflict.Furthermore, guest services representatives are not required tochallenge attendees at point of ingress 108, but can do so atsubstantially any suitable location associated with the venue.

It is understood that in some embodiments, system 100 can be included inattendee device 120, which can be a smart phone, a tablet, a wearablecomputer, or any other suitable device. Attendee device 120 can includea data store 122 that can retain various information, including ticketdata 112 that can be accessed by system 100. Furthermore, attendeedevice 120 can include user interface 116 that can comprise a display,microphone, speakers, camera, input mechanisms, and so forth.

Referring now to FIGS. 2A-B, illustrations 200 and 210 are provided.Illustration 200 depicts an example presentation with regard toproximity data being triggered by user input. Illustration 210 depictsan example presentation with regard to proximity data being triggered bytransmitters. As detailed previously, ticket data 112 can be redeemed inresponse to receipt of proximity data 104. In some embodiments,proximity data 104 can be triggered based on user input. For example,the attendee can, upon approaching point of ingress 108, manually inputinformation that indicates he or she is within defined distance 106 topoint of ingress 108, an example of which is provided by Illustration200. In this case, a display 202 included in user interface 116 canpresent message 204. Message 204 in this case presents the text “Justbefore you enter the venue, please select the following link to redeemyour ticket.” Display 204 also presents element 206 that can be a linkto redeem ticket. By selecting element 206 (or via another mechanism),proximity data 104 can be triggered and provided to system 100.Redemption component 110 can then validate ticket data 112, andpresentation component 114 can instruct user interface 116 to presentverification data 118 or associated indicia, possibly via display 202.As described, a guest services representatives at point of ingress 108can observe the presentation and allow entry to the venue.

Additionally or alternatively, in some embodiments, proximity data 104can be triggered in response to receiving a signal 214 from atransmitter 212 associated with the venue, an example of which isprovided in connection with illustration 210. This transmitter 212 canbe situated near point of ingress 108 or elsewhere and can be configuredto enable detection at defined distance 106, possibly based onenvironmental conditions, compliant equipment capabilities, or othercriteria. Signal 214 can be detected by a sensor 216 that can beincluded in system 100 and/or attendee device 120. It is appreciatedthat signal 214 can be an audio signal, in which case sensor 216 can bea microphone. Such an audio signal 214 can be configured for specificranges (e.g., defined distance 106) based on volume metrics, soundpressure metrics, or other suitable metrics and can be broadcast with afrequency that is beyond sensing capabilities of most humans, which canprovide a signal without interfering with the experience of attendees. Atypical human hearing range is between about 20 hertz to about 20kilohertz, so transmitters 212 that are audio transmitters can broadcastsound that is outside of this range, e.g., below about 20 hertz or aboveabout 20 kilohertz.

In other embodiments that can be implemented separately or together,transmitter(s) 212 can broadcast light-based signals that can bereceived by optical sensors 216, or be based on wireless communicationstandards that can be detected by an associated receiver mechanism.

Regardless of how it is determined that system 100 is in proximity topoint of ingress 108 (e.g., by user input that indicates such, bytransmitted signal detection, or another manner), such can triggerproximity data 104, which in turn can trigger ticket data 112 beingredeemed and verification data 118 being presented by user interface116. In some embodiments, proximity data 104 can include time datarelating to a current time/date. In such cases, redemption component 110can verify that the attendee is both near to point of ingress 108 andthat it is an appropriate time for entering the venue before redeemingticket data 112. Time data might also be used to determine when or howlong user interface 116 will present verification data 118. For example,if it is long past the time in which the event at the venue begins(and/or points of ingress 108 are closed), then verification data 118might not be presented by user interface 116.

Turning now to FIGS. 3A and 3B, illustrations 300 and 310 are provided.Illustration 300 relates to an example where verification data 118 ispresented visually. Illustration 310 relates to an example in whichverification data 118 is presented in an audible manner. In either case,presentation of verification data 118 can be facilitated by userinterface 116. For instance, illustration 300 depicts display device 202(of user interface 116) presenting verification data 118 in the form ofa visually observable message that states: “A valid ticket has beenredeemed. No scanning required.” This message can be presented to theguest services representative, which can be quickly verified and theattendee can be allowed entry to the venue with no scanning necessary.It is understood that the text message is merely an example, andverification data 118 can be presented in the form of an image or othervisual indicia, examples of which are provided in connection with FIGS.4A-C.

A similar procedure can occur in connection with illustration 310, butin this case presentation of verification data 118 can be formatted asan audio presentation. For instance, a speaker 312 associated with userinterface 116 can transmit verbal words perhaps in a distinctive voice,in this case stating that the attendee is authorized to enter the venue.In other examples, the verification data 118 might be a music clip or adistinctive sound byte. Such can be presented to the guest servicesrepresentative, who can quickly identify the sounds and allow entry.

Referring now to FIGS. 4A-C, illustrations 400, 410, and 420 areprovided. Illustrations 400, 410, and 420 relate to various examplepresentations of the verification data 118 that includes certificationdata 402 and/or indicia associated with certification data 402.Certification data 402 can relate to a certification that theverification data 118 (also being presented) is authentic. As oneexample, certification data 402 might be a word or phrase (e.g., code ofthe day). Presentation 400 depicts the word “Zeus” as certification data402. Hence, when a venue representative is presented attendee device 102that includes other verification data 118, seeing the word Zeus alsodisplayed can represent that the other verification data 118 isauthentic.

Presentation 410 provides an example in which certification data 402 isan image (e.g., a static image, an animated image, an image designed tothwart forwarding or copying, etc.), whereas presentation 420 providesan example in which certification data 402 is a background image. Theabove are intended to be non-limiting examples, and it is understoodthat certification data 402 can take many other forms and can besubstantially any suitable indicia. For instance, certification data 402might be a watermark, an audio presentation of some type or even amachine-readable code or string, which might utilize encryption aspects.It is understood that system 100 can take measures to securecertification data 402. For instance, the image of the bat and baseballin presentation 410 or the stadium image of presentation 420 might bepresentable to user interface 116, but not otherwise accessible by otherapplications utilized by attendee device 120.

With reference now to FIG. 5, system 500 is depicted. System 500 canfacilitate provision of venue-specific location data that can beutilized by a wide-range of attendee devices, even those not equippedwith other location-based services hardware such as GPS or the like. Forexample, a venue environment 502 can be populated with numeroustransmitters 504. Venue environment 502 can represent the interior ofthe venue (e.g., accessed via point of ingress 108), but in someembodiments can include the exterior of the venue, such as a venueparking lot. Transmitters 504 can be substantially similar totransmitter 212. For example, location data 506 can be transmitted tosystem 100 by some means, which can be a broadcast of sound and can beconfigured for a specific detection range and encoded with location data506. Upon receiving location data 506, system 100 can be apprised of acurrent location, generally one that is venue-specific such as nearpublic restrooms or parking lot 12. Location data 506 can be stored andrecalled later for various purposes such as for memorial purposes (e.g.,the route I took upon entering the stadium for game 6 of the WorldSeries), reminder purposes (e.g., parking location reminder), etc.

Location data 506 can also be utilized in connection with guidance ornavigation or for proximity-based alerts (e.g., “vendor 20 feet to thenorth is offering a free hot dog to attendees” or “please avoid thecurrent route due to a medical emergency”). Location data 506 can relateto permanent or fixed locations (e.g., restrooms) as well as transientor event-specific locations. For example, location data 506 can beemployed in connection with pre-event festivities, wherein a particularlocation is associated with service or other element only during adetermined period of time (e.g., only during the pre-event festivities,but not thereafter).

Referring now to FIG. 6, system 600 is illustrated. System 600 canprovide for the attendee device 120 operating as a transmitter, whichcan facilitate additional aspects of scannerless entry. For example, invarious embodiments detailed supra, although guest servicesrepresentatives are not required to scan ticket data, these guestservices representatives still function to check that verification data118 is being presented by the attendee device. Further efficiencies canbe achieved by removing such a check from the process of entry to thevenue. Such can be accomplished by system 600 that can include all orportions of system 100 and further include beacon component 602.

Beacon component 602 can be configured to facilitate transmission of aright of entry signal 604 to receiving device 606 associated with thevenue. For example, once proximity data 104 is triggered (e.g., based onan indication of proximity to point of ingress 108), ticket data 112 canbe validated and/or redeemed. Thereafter, rather than (or in additionto) causing user interface 116 to display indicia associated withverification data 118, beacon component 602 can facilitate transmissionof right of entry signal 604. Upon receipt of right of entry signal 604by receiving device 606, access limiting mechanism (e.g., a gate,turnstile, or the like) can be instructed to allow entry.

As with other signals detailed herein, right of entry signal 604 can bean audio signal, an optical signal, or based on a communication network.Audio signals can be advantageous because they do not requiresophisticated or expensive equipment to be included in attendee device,are not subject to network overload conditions, and can be readilyconfigured for a very small range such that interference can bemitigated and/or to ensure the signal is coming from one very close toreceiving device 606.

In some embodiments, right of entry signal 604 can be provided based onpassive transmission techniques. For example, an RFID dot can be adheredto attendee device. When exposed to an active RFID signal potentiallyincluded in or proximal to receiving device 606, the RFID dot respondswith right of entry signal 604. In this case, right of entry signal 604can include an identification associated with the attendee that can beverified in connection with allowing entry to the venue. In someembodiments, right of entry signal 604 can be transmitted according toactive techniques, and such might utilize RFID technologies, Bluetoothtechnologies, or be transmitted according to other wirelesscommunication standards.

Referring to FIG. 7, system 700 is provided. System 700 can provide foradditional features or aspects in connection with facilitatingscannerless entry to a venue. In this example, system 700 can includevenue validation device 702 that can be configured to validate attendeeID data 704. For example, when an attendee passes through point ofingress 108, venue validation device 702 can receive attendee ID data704, then determine, based on this ID data that the attendee has aprivilege to enter. If so, the attendee can be allowed entry. If not,attendee entrance can be restricted. Restricting access can beeffectuated by access limiting mechanism 608 or by guest servicesrepresentatives stationed at point of ingress 108. However, in thelatter case, these guest services representatives need not employscanners or even interact with the majority of attendees, but rather,only confront attendees for which attendee ID data 704 was notsuccessfully verified.

Attendee ID data 704 can be received in a variety of ways. As oneexample, attendee device 120 and/or system 100 can transmit attendee IDdata 704 according to substantially any technique described herein orotherwise suitable. Attendee ID data 704 can relate to a visual image,voice signatures or other signatures, an audio-based signal orwatermark, device ID, individual ID, biometric data such as afingerprint, retina, or DNA, etc. Thus, such attendee ID data 704 can besupplied by system 100 or directly by the attendee 710 (e.g., speakinginto a microphone for a voiceprint, providing a fingerprint, etc.).

Additionally or alternatively, point of ingress 108 can be equipped withimaging devices 706, which can include microphones or other sensordevices. These devices 706 can capture an image (or voiceprint) of apotential attendee. Associated data can be provided to component 708that can perform image processing as well as recognition techniques suchas facial recognition, voice recognition or the like and matchingprocesses. Such can be utilized to identify the attendee, and suchinformation can be transmitted to venue validation device 702 in theform of attendee ID data 704. Advantageously, attendee ID data 704 canbe further utilized for purposes of commemoration (e.g., images ofattendee at the venue can be provided to the attendee for memorializingthe occasion); marketing, rewards, or incentives; security; and so on.

Example Methods for Scannerless Venue Entry and Location Techniques

FIGS. 8 and 9 illustrate various methodologies in accordance withcertain embodiments of this disclosure. While, for purposes ofsimplicity of explanation, the methodologies are shown and described asa series of acts within the context of various flowcharts, it is to beunderstood and appreciated that embodiments of the disclosure are notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, those skilled in the art will understand andappreciate that a methodology can alternatively be represented as aseries of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the disclosed subject matter.Additionally, it is to be further appreciated that the methodologiesdisclosed hereinafter and throughout this disclosure are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers. The term article ofmanufacture, as used herein, is intended to encompass a computer programaccessible from any computer-readable device or storage media.

FIG. 8 illustrates exemplary method 800. Method 800 can provide forscannerless venue entry. For example, at reference numeral 802,proximity data indicating a place of ingress to a venue is within adefined distance from the attendee device can be received. For example,proximity data can be received in response to user input, wherein theuser indicates he or she is near to the place of ingress. As anotherexample, proximity data can be received in response to receipt ordetection of a signal broadcast by a transmitter situated at or near theplace of ingress or elsewhere.

At reference numeral 804, ticket data representing a privilege to enterthe venue can be validated. Validation of the privilege to enter thevenue can be validated in response to receiving the proximity data. Putanother way, a ticket purchased by an attendee can be redeemed inresponse to an indication that the attendee is near to the place ofentry to the venue.

At reference numeral 806, e.g., in response to redeeming the ticket, auser interface associated with the attendee device can be instructed topresent a verification that the ticket data was validated and/orredeemed. In other words, once the ticket is redeemed, the userinterface can display (or otherwise present) indicia that can inform tothis effect: that a valid ticket has been redeemed for this attendee.Accordingly, the attendee can present the display to a guest servicesrepresentative, who can observe the verification being displayed andallow entry to the venue without the need to employ scanning procedures.

In some embodiments, multiple tickets can be redeemed collectively, forinstance, by a single attendee device. For instance, five tickets can beredeemed for a family of five, and a single attendee device can beconfigured to display associated indicia. Such indicia might include anumber (e.g., “5”), images of the family members, or any suitableindicia to inform the guest services representative and/or authenticatethat all five individuals have a privilege of entry to the venue. Insome embodiments, the attendee device can specify how many tickets of aset of multiple tickets and/or which specific tickets from the set toredeem. For example, three members of the family of five might arrive atpoint of ingress at an earlier time than the other two. Accordingly, theattendee device can request input such as providing a display thatverifies whether all five tickets should be redeemed. In response inputcan be received indicating that only three of the five tickets (e.g., bypressing the number 3) should be redeemed.

It is understood that multiple ticket redemption can provide additionalconvenience for attendees, but also might be beneficial in situations inwhich some of the attendees do not possess a suitable device. Asdescribed supra, the attendee device can present verification data. Insome embodiments, seat locator data or other access privilege data canbe presented, such as, e.g., to gain access to interior or restrictedportions of the venue. However, attendees without a suitable device(e.g., one or more of the family of five) will not typically be able toaccomplish such. In this regard, in some embodiments, seat locator datacan be printed by a device at the point of ingress for all or a portionof the five-member family. In cases where the attendee does not haveaccess to a suitable device, this seat locator stub can be presented(e.g., to ushers in the interior of the venue), but otherwise, such canbe presented by the attendee device. In some embodiments, aspecial-purpose entry lane can be provided for multiple ticketredemption. This special-purpose entry lane can automatically print seatlocator stubs (or other suitable information) for some portion of thegroup of individual attendees that collectively redeemed tickets. Theseseat locator stubs might be printed for all members of the group otherthan the primary (e.g., the attendee device that redeemed tickets forthe group), or only for members in which no associated device isdetected.

FIG. 9 illustrates exemplary method 900. Method 900 can provide foradditional features or aspects in connection with providing scannerlessvenue entry and audio-based location techniques. For instance, atreference numeral 902, the proximity data (e.g., received in connectionwith reference numeral 802 of FIG. 8) can be received in response todetecting an audio signal broadcast by a transmitter device situatedproximal to the place of ingress.

Reference numerals 904 and 906 can relate to the instructionstransmitted to the user interface detailed in connection with referencenumeral 806 of FIG. 8. At reference numeral 904, the user interface canbe instructed to present a visual verification via a display deviceassociated with the user interface. This visual verification can be textor a particular image and can be configured for rapid verification by,e.g., a guest services representative stationed at the place of ingress.

At reference numeral 906, the user interface can be instructed topresent an audio verification via a speaker device associated with theuser interface. This audio verification can be part of a musicalcomposition, an oration, or another sound. As with the visualverification detailed at reference numeral 906, the audio verificationcan be configured for rapid verification by, e.g., a guest servicesrepresentative stationed at the place of ingress. For instance, theaudio verification can be a very distinctive voice, or a distinctiveportion of a musical composition or the like.

At reference numeral 908, the user interface can be instructed topresent a certification that a presentation of the verification isauthentic. This certification can be a defined background or otherimage, possibly including a watermark, certificate of authentication(COA), a code of the day, etc. In cases of an audio presentation, theverification can take the form of an audio watermark or an audio COA.

Example Operating Environments

The systems and processes described below can be embodied withinhardware, such as a single integrated circuit (IC) chip, multiple ICs,an application specific integrated circuit (ASIC), or the like. Further,the order in which some or all of the process blocks appear in eachprocess should not be deemed limiting. Rather, it should be understoodthat some of the process blocks can be executed in a variety of orders,not all of which may be explicitly illustrated herein.

With reference to FIG. 10, a suitable environment 1000 for implementingvarious aspects of the claimed subject matter includes a computer 1002.The computer 1002 includes a processing unit 1004, a system memory 1006,a codec 1035, and a system bus 1008. The system bus 1008 couples systemcomponents including, but not limited to, the system memory 1006 to theprocessing unit 1004. The processing unit 1004 can be any of variousavailable processors. Dual microprocessors and other multiprocessorarchitectures also can be employed as the processing unit 1004.

The system bus 1008 can be any of several types of bus structure(s)including the memory bus or memory controller, a peripheral bus orexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MCA), Extended ISA(EISA), Intelligent Drive Electronics (IDE), VESA Local Bus (VLB),Peripheral Component Interconnect (PCI), Card Bus, Universal Serial Bus(USB), Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1394), and SmallComputer Systems Interface (SCSI) or others now in existence or laterdeveloped.

The system memory 1006 includes volatile memory 109 and non-volatilememory 1012. The basic input/output system (BIOS), containing the basicroutines to transfer information between elements within the computer1002, such as during start-up, is stored in non-volatile memory 1012. Inaddition, according to present innovations, codec 1035 may include atleast one of an encoder or decoder, wherein the at least one of anencoder or decoder may consist of hardware, software, or a combinationof hardware and software. Although, codec 1035 is depicted as a separatecomponent, codec 1035 may be contained within non-volatile memory 1012or included in other components detailed herein. By way of illustration,and not limitation, non-volatile memory 1012 can include read onlymemory (ROM), programmable ROM (PROM), electrically programmable ROM(EPROM), electrically erasable programmable ROM (EEPROM), or flashmemory. Volatile memory 109 includes random access memory (RAM), whichacts as external cache memory. According to present aspects, thevolatile memory may store the write operation retry logic (not shown inFIG. 10) and the like. By way of illustration and not limitation, RAM isavailable in many forms such as static RAM (SRAM), dynamic RAM (DRAM),synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), andenhanced SDRAM (ESDRAM), resistive RAM (RRAM), or others now inexistence or later developed.

Computer 1002 may also include removable/non-removable,volatile/non-volatile computer storage medium. FIG. 10 illustrates, forexample, disk storage 1014. Disk storage 1014 includes, but is notlimited to, devices like a magnetic disk drive, solid state disk (SSD)floppy disk drive, tape drive, flash memory card, or memory stick. Inaddition, disk storage 1014 can include storage medium separately or incombination with other storage medium including, but not limited to, anoptical disk drive such as a compact disk ROM device (CD-ROM), CDrecordable drive (CD-R Drive), CD rewritable drive (CD-RW Drive) or adigital versatile disk ROM drive (DVD-ROM). To facilitate connection ofthe disk storage devices 1014 to the system bus 1008, a removable ornon-removable interface is typically used, such as interface 1016. It isappreciated that storage devices 1014 can store information related to auser. Such information might be stored at or provided to a server or toan application running on a user device. In one embodiment, the user canbe notified (e.g., by way of output device(s) 1036) of the types ofinformation that are stored to disk storage 1014 and/or transmitted tothe server or application. The user can be provided the opportunity toauthorize having such information collected and/or shared with theserver or application (e.g., by way of input from input device(s) 1028).

It is to be appreciated that FIG. 10 describes software that acts as anintermediary between users and the basic computer resources described inthe suitable operating environment 1000. Such software includes anoperating system 1018. Operating system 1018, which can be stored ondisk storage 1014, acts to control and allocate resources of thecomputer system 1002. Applications 1020 take advantage of the managementof resources by operating system 1018 through program modules 1024, andprogram data 1026, such as the boot/shutdown transaction table and thelike, stored either in system memory 1006 or on disk storage 1014. It isto be appreciated that the claimed subject matter can be implementedwith various operating systems or combinations of operating systems.

A user enters commands or information into the computer 1002 throughinput device(s) 1028. Input devices 1028 include, but are not limitedto, a pointing device such as a mouse, stylus, touch pad, keyboard,microphone, joystick, game pad, satellite dish, scanner, TV tuner card,digital camera, digital video camera, web camera, and the like. Theseand other input devices connect to the processing unit 1004 through thesystem bus 1008 via interface port(s) 1030. Interface port(s) 1030include, for example, a serial port, a parallel port, a game port, and auniversal serial bus (USB). Output device(s) 1036 use some of the sametype of ports as input device(s) 1028. Thus, for example, a USB port maybe used to provide input to computer 1002 and to output information fromcomputer 1002 to an output device 1036. Output adapter 1034 is providedto illustrate that there are some output devices 1036 like monitors,speakers, and printers, among other output devices 1036, which requirespecial adapters. The output adapters 1034 include, by way ofillustration and not limitation, video and sound cards that provide ameans of connection between the output device 1036 and the system bus1008. It should be noted that other devices and/or systems of devicesprovide both input and output capabilities such as remote computer(s)1038.

Computer 1002 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1038. The remote computer(s) 1038 can be a personal computer, a server,a router, a network PC, a workstation, a microprocessor based appliance,a peer device, a smart phone, a tablet, or other network node, andtypically includes many of the elements described relative to computer1002. For purposes of brevity, only a memory storage device 1040 isillustrated with remote computer(s) 1038. Remote computer(s) 1038 islogically connected to computer 1002 through a network interface 1042and then connected via communication connection(s) 1044. Networkinterface 1042 encompasses wire and/or wireless communication networkssuch as local-area networks (LAN) and wide-area networks (WAN) andcellular networks. LAN technologies include Fiber Distributed DataInterface (FDDI), Copper Distributed Data Interface (CDDI), Ethernet,Token Ring and the like. WAN technologies include, but are not limitedto, point-to-point links, circuit switching networks like IntegratedServices Digital Networks (ISDN) and variations thereon, packetswitching networks, and Digital Subscriber Lines (DSL).

Communication connection(s) 1044 refers to the hardware/softwareemployed to connect the network interface 1042 to the bus 1008. Whilecommunication connection 1044 is shown for illustrative clarity insidecomputer 1002, it can also be external to computer 1002. Thehardware/software necessary for connection to the network interface 1042includes, for exemplary purposes only, internal and externaltechnologies such as, modems including regular telephone grade modems,cable modems and DSL modems, ISDN adapters, and wired and wirelessEthernet cards, hubs, and routers.

Referring now to FIG. 11, there is illustrated a schematic block diagramof a computing environment 1100 in accordance with this specification.The system 1100 includes one or more client(s) 1102 (e.g., laptops,smart phones, PDAs, media players, computers, portable electronicdevices, tablets, and the like). The client(s) 1102 can be hardwareand/or software (e.g., threads, processes, computing devices). Thesystem 1100 also includes one or more server(s) 1104. The server(s) 1104can also be hardware or hardware in combination with software (e.g.,threads, processes, computing devices). The servers 1104 can housethreads to perform transformations by employing aspects of thisdisclosure, for example. One possible communication between a client1102 and a server 1104 can be in the form of a data packet transmittedbetween two or more computer processes wherein the data packet mayinclude video data. The data packet can include a cookie and/orassociated contextual information, for example. The system 1100 includesa communication framework 1106 (e.g., a global communication networksuch as the Internet, or mobile network(s)) that can be employed tofacilitate communications between the client(s) 1102 and the server(s)1104.

Communications can be facilitated via a wired (including optical fiber)and/or wireless technology. The client(s) 1102 are operatively connectedto one or more client data store(s) 1108 that can be employed to storeinformation local to the client(s) 1102 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1104 areoperatively connected to one or more server data store(s) 1110 that canbe employed to store information local to the servers 1104.

In one embodiment, a client 1102 can transfer an encoded file, inaccordance with the disclosed subject matter, to server 1104. Server1104 can store the file, decode the file, or transmit the file toanother client 1102. It is to be appreciated, that a client 1102 canalso transfer uncompressed file to a server 1104 and server 1104 cancompress the file in accordance with the disclosed subject matter.Likewise, server 1104 can encode video information and transmit theinformation via communication framework 1106 to one or more clients1102.

The illustrated aspects of the disclosure may also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Moreover, it is to be appreciated that various components describedherein can include electrical circuit(s) that can include components andcircuitry elements of suitable value in order to implement theembodiments of the subject innovation(s). Furthermore, it can beappreciated that many of the various components can be implemented onone or more integrated circuit (IC) chips. For example, in oneembodiment, a set of components can be implemented in a single IC chip.In other embodiments, one or more of respective components arefabricated or implemented on separate IC chips.

What has been described above includes examples of the embodiments ofthe present invention. It is, of course, not possible to describe everyconceivable combination of components or methodologies for purposes ofdescribing the claimed subject matter, but it is to be appreciated thatmany further combinations and permutations of the subject innovation arepossible. Accordingly, the claimed subject matter is intended to embraceall such alterations, modifications, and variations that fall within thespirit and scope of the appended claims. Moreover, the above descriptionof illustrated embodiments of the subject disclosure, including what isdescribed in the Abstract, is not intended to be exhaustive or to limitthe disclosed embodiments to the precise forms disclosed. While specificembodiments and examples are described herein for illustrative purposes,various modifications are possible that are considered within the scopeof such embodiments and examples, as those skilled in the relevant artcan recognize. Moreover, use of the term “an embodiment” or “oneembodiment” throughout is not intended to mean the same embodimentunless specifically described as such.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms used to describe such components are intended to correspond,unless otherwise indicated, to any component which performs thespecified function of the described component (e.g., a functionalequivalent), even though not structurally equivalent to the disclosedstructure, which performs the function in the herein illustratedexemplary aspects of the claimed subject matter. In this regard, it willalso be recognized that the innovation includes a system as well as acomputer-readable storage medium having computer-executable instructionsfor performing the acts and/or events of the various methods of theclaimed subject matter.

The aforementioned systems/circuits/modules have been described withrespect to interaction between several components/blocks. It can beappreciated that such systems/circuits and components/blocks can includethose components or specified sub-components, some of the specifiedcomponents or sub-components, and/or additional components, andaccording to various permutations and combinations of the foregoing.Sub-components can also be implemented as components communicativelycoupled to other components rather than included within parentcomponents (hierarchical). Additionally, it should be noted that one ormore components may be combined into a single component providingaggregate functionality or divided into several separate sub-components,and any one or more middle layers, such as a management layer, may beprovided to communicatively couple to such sub-components in order toprovide integrated functionality. Any components described herein mayalso interact with one or more other components not specificallydescribed herein but known by those of skill in the art.

In addition, while a particular feature of the subject innovation mayhave been disclosed with respect to only one of several implementations,such feature may be combined with one or more other features of theother implementations as may be desired and advantageous for any givenor particular application. Furthermore, to the extent that the terms“includes,” “including,” “has,” “contains,” variants thereof, and othersimilar words are used in either the detailed description or the claims,these terms are intended to be inclusive in a manner similar to the term“comprising” as an open transition word without precluding anyadditional or other elements.

As used in this application, the terms “component,” “module,” “system,”or the like are generally intended to refer to a computer-relatedentity, either hardware (e.g., a circuit), a combination of hardware andsoftware, software, or an entity related to an operational machine withone or more specific functionalities. For example, a component may be,but is not limited to being, a process running on a processor (e.g.,digital signal processor), a processor, an object, an executable, athread of execution, a program, and/or a computer. By way ofillustration, both an application running on a controller and thecontroller can be a component. One or more components may reside withina process and/or thread of execution and a component may be localized onone computer and/or distributed between two or more computers. Further,a “device” can come in the form of specially designed hardware;generalized hardware made specialized by the execution of softwarethereon that enables the hardware to perform specific function; softwarestored on a computer readable medium; or a combination thereof.

Moreover, the words “example” or “exemplary” are used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe words “example” or “exemplary” is intended to present concepts in aconcrete fashion. As used in this application, the term “or” is intendedto mean an inclusive “or” rather than an exclusive “or”. That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform.

Computing devices typically include a variety of media, which caninclude computer-readable storage media and/or communications media, inwhich these two terms are used herein differently from one another asfollows. Computer-readable storage media can be any available storagemedia that can be accessed by the computer, is typically of anon-transitory nature, and can include both volatile and nonvolatilemedia, removable and non-removable media. By way of example, and notlimitation, computer-readable storage media can be implemented inconnection with any method or technology for storage of information suchas computer-readable instructions, program modules, structured data, orunstructured data. Computer-readable storage media can include, but arenot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal that can betransitory such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

What is claimed is:
 1. An attendee device, comprising: a memory to store computer executable components; and a processor that executes the following computer executable components stored in the memory: a communication component that receives ticket data indicative of a privilege to enter a venue; a redemption component that performs a self-validation procedure in which the attendee device validates the ticket data and, in response to the ticket data being validated, generates at least a portion of verification data that is representative of an indication the ticket data was validated; a proximity component that determines whether the attendee device is within a defined distance range from a point of ingress to the venue in which entry is challenged in response to the verification data not being presented by a user interface of the attendee device; and a presentation component that instructs the user interface of the attendee device to present the verification data in response to one or more conditions being determined to be met, wherein a first condition of the one or more conditions is the proximity component has determined that the attendee device is within the defined distance range.
 2. The attendee device of claim 1, wherein the proximity component determines the system is within the defined distance range in response to input to the user interface that indicates the system is within the defined distance range.
 3. The attendee device of claim 1, wherein the proximity component determines the system is within the defined distance range in response to detection of an acoustic signal from a transmitter of the venue.
 4. The attendee device of claim 3, wherein the communication component receives a second portion of the verification data in response to the one or more conditions being determined to be met.
 5. The attendee device of claim 1, wherein the privilege to enter the venue is in connection with a specific event being held at the venue, and wherein the proximity component determines a current time is within a defined temporal range of a time associated with the event.
 6. The attendee device of claim 5, wherein a second condition of the one or more conditions is the proximity component has determined the current time is within the defined temporal range.
 7. The attendee device of claim 1, wherein the self-validation procedure comprises an attendee device comprising the redemption component validating the ticket data without the ticket data being scanned by a venue device at the point of ingress.
 8. The attendee device of claim 1, wherein the verification data presented by the user interface relates to visual indicia.
 9. The attendee device of claim 1, wherein the verification data presented by the user interface relates to acoustic indicia.
 10. The attendee device of claim 1, wherein the presentation component instructs the user interface to present certification data in conjunction with presentation of the verification data, wherein the certification data represents a certification the verification data is authentic.
 11. The attendee device of claim 1, wherein the proximity component further receives location data that represents a current location of the system and a target location associated with a defined destination.
 12. The attendee device of claim 1, further comprising a beacon component that facilitates transmission of a right of entry signal to a device associated with the venue, wherein the right of entry signal encodes information that indicates a privilege to enter the venue.
 13. The system attendee device of claim 12, wherein the right of entry signal is at least one of an audio signal, an active radio frequency identification (RFID) signal, a passive RFID signal triggered in response to an active RFID signal received from a device associated with the venue, a Bluetooth signal, or a near field communication (NFC) signal.
 14. The attendee device of claim 1, wherein the point of ingress relates to at least one of: ingress to the venue, ingress to a portion of the venue, or ingress to a parking area associated with the venue.
 15. The system attendee device of claim 1, further comprising a beacon component that, in response to the privilege to enter being validated, transmits a right of entry signal to a receiving device associated with the venue.
 16. The system attendee device of claim 15, wherein the receiving device facilitates presentation of indicia indicating the privilege to enter was validated.
 17. The attendee device of claim 15, wherein the receiving device instructs an access limiting mechanism to grant access.
 18. A method, comprising: employing a computer-based processor included in an attendee device to execute computer executable components stored in a memory to perform the following: receiving ticket data representing a privilege to enter a venue hosting an event; performing a self-validation procedure that validates the ticket data; generating at least a portion of verification data that indicates the ticket data was validated and the privilege to enter the venue is authorized; determining a place of ingress to the venue is within a defined distance from the attendee device, wherein the place of ingress is a scannerless place of ingress that does not require ticket data to be examined and wherein entry to the venue is challenged without a presentation of the verification data; and instructing a user interface of the attendee device to present the verification data, wherein the instructing is triggered in response to a determination that at least one condition has been satisfied, wherein the at least one condition comprises a first condition that attendee device is within the defined distance from the place of ingress.
 19. The method of claim 18, wherein the receiving proximity data is in response to detecting an acoustic signal broadcast by a transmitter device situated proximal to the place of ingress.
 20. The method of claim 18, wherein the instructing the user interface comprising instructing the user interface to present a visual verification via a display device of the user interface.
 21. The method of claim 18, wherein the instructing the user interface comprising instructing the user interface to present an acoustic verification via a speaker device of the user interface.
 22. The method of claim 18, further comprising instructing the user interface to present a certification that a presentation of the verification is authentic.
 23. A non-transitory computer readable storage medium storing computer-executable instructions that, in response to execution, cause an attendee device including a processor to perform operations, comprising: receiving ticket data representative of a privilege to enter a venue; determining a point of ingress to the venue is within a defined distance, wherein entry to the venue is challenged in response to verification data verification data not being presented; redeeming the ticket data according to a self-redemption procedure by which the attendee device validates the privilege to enter the venue without the ticket data being scanned at the point of ingress by a venue device, wherein the self-redemption procedure is triggered in response to the determining the point of ingress is within the defined distance; and instructing a user interface associated with the attendee device to present the verification data representing a verification that the ticket data was redeemed.
 24. The non-transitory computer readable storage medium of claim 23, wherein the determining the point of ingress is within the defined distance is in response to detection of an acoustic signal transmitted by a transmitter device associated with the venue.
 25. The non-transitory computer readable storage medium of claim 23, wherein the verification data comprises visual indicia suitable for presentation by a display device of the user interface.
 26. The non-transitory computer readable storage medium of claim 23, wherein the verification data comprises acoustic indicia suitable for presentation by a speaker device of the user interface. 